-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump rails from 7.0.8 to 7.1.0 #5031
Conversation
Bumps [ddtrace](https://github.com/DataDog/dd-trace-rb) from 1.14.0 to 1.15.0. - [Release notes](https://github.com/DataDog/dd-trace-rb/releases) - [Changelog](https://github.com/DataDog/dd-trace-rb/blob/master/CHANGELOG.md) - [Commits](DataDog/dd-trace-rb@v1.14.0...v1.15.0) --- updated-dependencies: - dependency-name: ddtrace dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [rails](https://github.com/rails/rails) from 7.0.8 to 7.1.0. - [Release notes](https://github.com/rails/rails/releases) - [Commits](rails/rails@v7.0.8...v7.1.0) --- updated-dependencies: - dependency-name: rails dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Changes made by me:
|
…u/dodona into dependabot/bundler/rails-7.1.0
This reverts commit 927e283.
Next steps applied by me: I applied the new rails defaults one by one as specified here: 41635ce and then update the new default configs to 7.1 Notable changes:
I had to use I have also not yet updated Todo
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything seems to still work.
The require_relative
is probably due to https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#autoloaded-paths-are-no-longer-in-$load-path.
Do we have an issue (or can we fix them now?) to track deprecation warnings, such as:
DEPRECATION WARNING: DeprecatedConstantAccessor.deprecate_constant without a deprecator is deprecated (called from <top (required)> at /home/niko/Ontwikkeling/dodona/config/application.rb:7)
DEPRECATION WARNING: Support for the pre-Ruby 2.4 behavior of to_time has been deprecated and will be removed in Rails 7.2. (called from <top (required)> at /home/niko/Ontwikkeling/dodona/config/initializers/new_framework_defaults.rb:17)
DEPRECATION WARNING: `Rails.application.secrets` is deprecated in favor of `Rails.application.credentials` and will be removed in Rails 7.2. (called from <top (required)> at /home/niko/Ontwikkeling/dodona/config/environment.rb:11)
I agree https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#autoloaded-paths-are-no-longer-in-$load-path is the cause of the change. Do you prefer the current solution or adding |
I have solved:
I just allowed the new setting. We only used I haven't seen:
I also do not see why we get this error as we already use the new credentials system instead of secrets. Could it be that you still have an old The last depecreation error is probably caused by one of our dependencies as it is mentioned when running
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if I understand it correctly no require should be needed at all because autoload fixes this? It is odd that the tests fail 1 out of 5 times without any require statement.
It is indeed a weird issue, as the failures are a bit flaky (although they do seem to happen a lot more if running tests in parallel than when running in a single process).
Do you prefer the current solution or adding
config.add_autoload_paths_to_load_path = true
to the test config?
I think the current solution is fine.
I did have a secrets file around, and as long as we don't cause deprecation warnings, no issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add the changes from #5027 to this PR? This will simplify a potential rollback.
Bumps rails from 7.0.8 to 7.1.0.
Release notes
Sourced from rails's releases.
... (truncated)
Commits
d39db5d
Preparing for 7.1.0 release4cc7947
Merge pull request #49491 from tnir/tn-date-rails71d206e8c
Release notes are not in work in progress anymore60393bb
Merge pull request #49493 from skipkayhil/hm-no-backticks9826678
Add corrected release month for Rails 7.1525b09c
Add release month for Rails 7.1b6842b2
Merge pull request #49391 from ipc103/transaction-tracking-on-reconnect311f639
Merge pull request #49487 from yawboakye/clarify-login-procedure-expectationf05e283
Merge pull request #49484 from hachi8833/fix_heading_migration_guide4280a03
Merge pull request #49480 from hachi8833/add_doc_db_prepareDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditions